
APAR= II09522
INSTALLING OS/400 AND CA/400 WINDOWS 95 FROM A BACKUP CD


** Last updated 10/30/96 **

When using a backup CD labeled with a media number ending in
"00" (LCD4-nnnn-00) to re-install both OS/400 and Client
Access/400 for Windows 95, the following process should
be followed:

1. Install OS/400
2. Load/apply PTF SF35445
3. Install Client Access/400 for Windows 95

Note: This process is not necessary when using a backup CD
      labeled with a "01" suffix.

If this process is not followed, Client Access/400 for Windows
95 will not install properly on the AS/400 under the following
two scenarios.  The install will appear to have completed
successfully with no failure messages or indicators given.

1. Non US English installations of 5763XD1 (Win95) on the AS/400
2. All upgrades from V3R1M0 Win95 to V3R1M1 Win95 on the AS/400


1. Non US English installations of 5763XD1 (Win95) on the AS/400
----------------------------------------------------------------
There are 2 ways that customers will see the problem with this
scenario:

- creating install media
- upgrading PCs at V3R1M0 Win95 to V3R1M1 Win95

If the customer creates their own install diskettes or copies
the qca400win32installcdrom image to a PC server and
installs the Win95 client code on a PC, the installation will
be US English instead of the native language they are
expecting.  The PC screens to install will be in English.

If a customer has V3R1M0 Win95, which was English only,
installed on the PC and connects to an AS/400 that has V3R1M1
Win95 native language, an upgrade will occur.  The upgrade
will be English when the user will expect it to be a native
language upgrade.  The customer will see PC screens indicating
an upgrade/installation is to occur, but these will be in
English.


2. All upgrades from V3R1M0 Win95 to V3R1M1 Win95 on the AS/400
---------------------------------------------------------------
If the customer has V3R1M0 Win95 installed on the AS/400 and
upgrades to V3R1M1 on the AS/400, client MRI and some code
files in the qca400win32install... path will not be
updated.

When the PC connects to the AS/400, the PC will autodetect
that an upgrade needs to occur.  The upgrade will download
the code and MRI files from the AS/400.

It may not be immediately obvious to the user that a mismatch
of code/MRI files exists on the PC.  The following types of
problems may result from the mismatch:

- Options new to the upgrade may not be displayed/available
  on the PC
- Unexpected results


Recovery
--------
The recovery on the AS/400 is done by:

- Remove 5763XD1 from the AS/400 using the DLTLICPGM AS/400
  command.
- Load/Apply SF35445 or slip install V3R7 OS/400 from media
  other than the backup CD.
- Install 5763XD1 on the AS/400 using the RSTLICPGM AS/400
  command.
- Load/Apply any 5763XD1 Service Packs/PTFs that were
  previously installed (the DLTLICPGM removes them).

The recovery on the PC is done by:

- If the PC was updated to V3R1M1 as described above, the
  product needs to be re-installed on the PC.  The user can
  run the SETUP.EXE program from qca400win32installcdrom
  directory or from the V3R1M1 PC install media shipped to
  them.  They should be able to install over the incorrect
  installation.

  NOTE: The cleanest PC re-installation would be to remove
  the CA/400 code from the PC, and then install CA/400 again.
  Accomplish this by employing the Add/Remove Programs icon
  in the Windows 95 Control Panel.  Then use the install media
  to install CA/400 again.  The install media can contain
  V3R1M0 or V3R1M1 CA/400... either is fine because the PC
  will migrate or update via "Login Service Check" when it
  connects to the AS/400.

- If the PC was not updated to V3R1M1 as described above, the
  PC should automatically update itself once the customer has
  corrected the installation on the AS/400 the next time the
  PC connects to the AS/400.


* SPECIAL NOTE *
 Within this Informational APAR there are some directory
 paths listed.  This tool does not handle the backslash
 correctly so a "" has been inserted for all backslashes.
 Please replace all the "" with a backslash.


